Repository navigation
[deps]: Update Microsoft.NET.Test.Sdk to v18.12.0 - #8728
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Collaborator
|
Internal tracking:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8728 +/- ##
=======================================
Coverage 68.82% 68.83%
=======================================
Files 2756 2756
Lines 118233 118233
Branches 10862 10862
=======================================
+ Hits 81375 81382 +7
+ Misses 34303 34298 -5
+ Partials 2555 2553 -2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
renovate
Bot
force-pushed
the
renovate/vstest-monorepo
branch
from
October 26, 2026 15:51
7aebb06 to
9d6cdf7
Compare
renovate
Bot
force-pushed
the
renovate/vstest-monorepo
branch
from
November 17, 2026 19:46
9d6cdf7 to
034049b
Compare
renovate
Bot
force-pushed
the
renovate/vstest-monorepo
branch
from
November 18, 2026 15:11
034049b to
ce46078
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
[18.7.0]→[18.12.0]Release Notes
microsoft/vstest (Microsoft.NET.Test.Sdk)
v18.12.0Security fix
This release includes the fix for CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.11.0 and earlier. Every version from 18.11.1 on is fixed, including 18.12.0.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: #16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See #16652
What's Changed
Full Changelog: microsoft/vstest@v18.11.0...v18.12.0
v18.11.1Security fix
This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.11.0.Fixed in:
Microsoft.TestPlatform.CLI18.11.1.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: #16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See #16652
What's Changed
Full Changelog: microsoft/vstest@v18.11.0...v18.11.1
v18.11.0What's Changed
New Contributors
Full Changelog: microsoft/vstest@v18.10.1...v18.11.0
v18.10.2Security fix
This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.10.0 and 18.10.1.Fixed in:
Microsoft.TestPlatform.CLI18.10.2.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: #16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See #16652
What's Changed
Full Changelog: microsoft/vstest@v18.10.1...v18.10.2
v18.10.1What's Changed
Full Changelog: microsoft/vstest@v18.10.0...v18.10.1
v18.10.0What's Changed
vstest.consoleand datacollector by @nohwnd in #16201Full Changelog: microsoft/vstest@v18.9.0...v18.10.0
v18.9.0What's Changed
New Contributors
Full Changelog: microsoft/vstest@v18.8.0...v18.9.0
v18.8.1What's Changed
Full Changelog: microsoft/vstest@v18.8.0...v18.8.1
v18.8.0What's Changed
Full Changelog: microsoft/vstest@v18.7.0...v18.8.0
v18.7.1Security fix
This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.7.0.Fixed in:
Microsoft.TestPlatform.CLI18.7.1.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: #16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See #16652
What's Changed
Full Changelog: microsoft/vstest@v18.7.0...v18.7.1
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.